home *** CD-ROM | disk | FTP | other *** search
- Date: Tue, 7 Jun 1994 02:43:03 -0400 (EDT)
- From: Timothy Miller <millert@undergrad.csee.usf.edu>
- Subject: Re: Digested
- To: gem-list@world.std.com
- In-Reply-To: <9406070324.AA29847@uqcspe.cs.uq.oz.au>
- Message-Id: <Pine.3.87.9406070203.A29815-0100000@undergrad>
- Mime-Version: 1.0
- Precedence: bulk
-
- Ofir was nice enough to give me a comprehensive list of amodal dialog
- handlers for various programming languages, including all the complaints
- about them.
-
- So, I spend the past couple hours putting together my own amodal
- form_do thingy. Actually, it's not really amodal, per se... it just
- allows DA's and apps to have their dialog in a window so it doesn't get
- in the way of OTHER apps and DAs. For now. My intention is to make it
- REALLY amodal so the app itself can have more than one non-conflicting
- dialog-in-a-window, but I haven't seen how any of the others handle this,
- so I have no idea how to do it with a tremendous degree of elegance.
- It sure would be nice to have C++, but I'm stuck with Lattice C.
-
- It has no frills. When a button or edit object is clicked on, form_button
- and form_keybd are called, etc. No Ctrl or Alt keys handled yet (although
- that shouldn't be tough). I was working on the ability to click and place
- the edit cursor anywhere within an editable field, but that turned out to
- be harder than I thought, so I haven't finished it.
-
- How are pop-up menus done? Aren't they handled by the app when the user
- clicks on a button that corresponds to it? I could handle that sort of
- thing in my library, but perhaps not.
-
- If I can get source code to any of the others around, I'll see what
- concepts I can 'borrow'.
-
- Email me privately.
-
-
-